Opcon, OMS, CSI, DCSR Server Recovery

Services Involved

Impacts

Response

Services MAY include any  of the following:

CSI, Opcon, OMS, OMSBridge, Drop Copy Reader

 

Service Types MAY include any  of the following:

CSI, OCS, OMS, OMSB, DSCR, and

DLCS, BLOC, DLOM

 

During Off-Trading and Trading Hours:

- No trading suspension considerations are necessary. 

 

-System monitoring will be compromised.  EMT will not receive messages from Opcon until problems resolved.

 

-Administrative functions and queries from CSI will not be possible.

 

-Brokerplex, FSD and CSI messaging to Matching Engines and/or Order Sending Firms will be queued until OMS and OMSBridge processes are restarted.

 

- Matching Engine drop copies to Order Sending Firms will be queued in 29west Data Store until DCSR process is restarted.

 

- Notify EXECUTIVE and IBs that OMSBridge connectivity between BPLX and ME is compromised.

 

- Move applications to alternate nodes.

- If alternate nodes not available, move to DR nodes.

- All hosts and host specific configurations are pre-defined, outside of JNLP requirements for CSI client connections.  These files must be changed to allow CSI client connectivity.

 

Restart order (as applicable by server):

OCS (followed by confirmation of monitoring integrity), OMSB, OMS, DCSR, CSI, then database loaders.

 

- Confirm all data accounted for around move.

 

- Database loader files can be concatenated after end of day shutdown.

 

SEE APPLICATION SPECIFIC RECOVERY DOCUMENTATION FOR MORE INFORMATION, IF NEEDED.